One-segment PUCCH formats

ABSTRACT

A user equipment (UE) that performs control signal transmission according to a single-segment subframe format is described. In an aspect, the UE selects a single-segment subframe format as an uplink transmission format for a subframe instead of a multi-segment subframe format. This selection may be based on an indication received by a network node that the single-segment subframe format is to be used for transmission of the one or more control signals. In addition, the UE transmits the one or more control signals on an uplink control channel using the single-segment subframe format.

RELATED APPLICATIONS

This application is a continuation of prior U.S. application Ser. No.16/563,182, filed 6 Sep. 2019, which is a continuation of prior U.S.application Ser. No. 15/766,851, filed 9 Apr. 2018, U.S. patent Ser. No.10/454,647), which is the National Stage of International ApplicationPCT/SE2017/050818, filed 14 Aug. 2017, which claims benefit of U.S.Provisional Application 62/374,495, filed 12 Aug. 2016, and U.S.Provisional Application 62/401,490, filed 29 Sep. 2016, the entiredisclosure of each being hereby incorporated by reference herein.

TECHNICAL FIELD

The present disclosure generally relates to a wireless communicationsystem, and specifically relates to uplink control channel transmissionswithin the wireless communication system.

BACKGROUND

In current wireless communication systems, a user equipment (UE)communicates with a network node (such as a base station, eNB, or othernetwork device) to receive data over one or more downlink channels in acell associated with the network node. To maintain channel and datatransfer integrity, the UE may likewise transmit control signaling tothe network node on one or more uplink channels. For instance, uplinkcontrol signaling from the UE to the network node can include hybridautomatic repeat request (HARQ or H-ARQ) acknowledgements for receiveddownlink data, UE reports related to the downlink channel conditionsthat are used as assistance for the downlink scheduling, and/orscheduling requests indicating that the UE requires uplink resources foruplink data transmissions.

This uplink control signaling can be transmitted, for example, on aPhysical Uplink Control Channel (PUCCH), which presently adheres to amulti-segment subframe structure according to which uplink controlsignal transmissions are scheduled by a network node in the time andfrequency domains. Specifically, a typical Long-Term Evolution (LTE)subframe is 1 ms in length and contains two 0.5 ms slots each having anumber (e.g., six or seven) of symbols. A number of resource elementscorresponding to the available system bandwidth are allocated by anetwork-side scheduler to one or more UEs in a cell for uplink controltransmission during the subframe.

In some subframes, one or more resource elements in a final symbol ofthe subframe (in the second slot) is reserved for UE transmission of asounding reference signal (SRS), which is received by the network nodeand processed to determine characteristics (e.g., channel quality,interference, etc.) of the uplink control channel. In some instances,the UEs may be configured to perform frequency hopping for SoundingReference Signal (SRS) transmissions. When such switching occurs, adelay in SRS transmission may occur as a result of a signal amplifieradjusting a power level from a first power level associated with PUCCHtransmissions to a second power level associated with SRS transmission.In some cases, this delay does not affect control signal transmission oroverall performance in the cell. Where, however, the delay reaches athreshold duration (e.g., ˜symbol duration), the SRS may be delayedenough so as to overlap in time and frequency with scheduled PUCCHtransmissions in the cell, causing signal “collision.” To avoid thisscenario, which introduces interference that can render one or both ofthe SRS and PUCCH undiscernible by the receiver, one or more subsequentslots may be cancelled, or “dropped,” resulting in wasted systemresources and decreased system throughput.

Thus, improved uplink control frame structures and related techniquesfor uplink signal scheduling are needed to improve system performance insituations where signal collision occurs or may occur.

SUMMARY

One or more embodiments herein can employ multiple different potentialsingle-segment subframes that define different possible techniques fortransmitting uplink control data on an uplink control channel in awireless environment. Some embodiments may therefore dynamically selecta format for one or more uplink subframes from one of the multipledifferent potential single-segment subframe formats and multi-segmentsubframe formats. In some examples, a network node or the UE operatingin a cell may select a single-segment subframe format for the subframewhere it is determined that SRS hopping is implemented by the UE and/oran actual or potential collision event is detected between the SRS andother uplink data in the cell. Allowing a single-segment subframe to bedynamically selected in this way may, for example, advantageously avoidcollision between uplink transmission in the cell and the potentialdropping of one or more uplink transmission slots that can result fromcollision.

More particularly, embodiments herein include a method performed by a UEfor control signal transmission, which may include selecting asingle-segment subframe format as an uplink transmission format for asubframe instead of a multi-segment subframe format. In addition, such amethod may include the UE transmitting one or more control signals on anuplink control channel using the single-segment subframe format. Theselection may be temporary, wherein the UE applies the single-segmentsubframe format for a specific amount of time and then reverts to themulti-segment subframe format; alternatively, the single-segmentsubframe format may be applied in an open-ended fashion, e.g., until themulti-segment subframe format is selected, until control transmissionsare interrupted, or the like. Further alternatively, the UE may decideto switch between transmitting the single-segment subframe format (e.g.,a short PUCCH format) and the multi-segment subframe format (e.g., along PUCCH format), depending on the size and/or the content of UplinkControl Information to be transmitted; this may be practiced regardlessof whether a component carrier switch is to be performed for a soundingreference signal.

Embodiments herein also include corresponding apparatus, computerprograms, and carriers (e.g., computer program products), as well asnetwork-side aspects performed by a network node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a wireless communication system accordingto one or more embodiments.

FIG. 2 is a logical flow diagram illustrating a method performed by a UEaccording to one or more embodiments.

FIG. 3 is a logical flow diagram illustrating a method performed by anetwork node according to one or more embodiments.

FIG. 4A is a block diagram of a UE according to one or more embodiments.

FIG. 4B is a block diagram of a UE according to one or more otherembodiments.

FIG. 5A is a block diagram of a radio node according to one or moreembodiments.

FIG. 5B is a block diagram of a radio node according to one or moreother embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates a wireless communication system 10 according to oneor more embodiments. The system 10 includes a network node 106 (such as,but not limited to, a base station, eNB, gNB, etc). The system 10 alsoincludes a UE 102 (also referred to herein as a “terminal, “userterminal,” or the like) in communication with the network node 106. Thiscommunication, in addition to uplink and downlink transmission ofuser/application data, may include uplink control signaling 20 anddownlink control signaling 18. In some examples, the uplink controlsignaling 20 may be performed over a PUCCH or Physical Uplink SharedChannel (PUSCH). In some examples, if the UE 102 has been assignedresources for data transmission in the current subframe, uplink controlinformation (including HARQ acknowledgements) is transmitted togetherwith data on the PUSCH. On the PUCCH, if the terminal has not beenassigned resources for data transmission in the current subframe, uplinkcontrol information is transmitted separately from user data, usingresource blocks specifically assigned for the purpose. The uplinkcontrol signaling 20 may include HARQ acknowledgements for receiveddownlink data, terminal reports related to the downlink channelconditions, uplink scheduling requests, and/or SRS transmissions. Thedownlink control signaling 18 may include uplink control channelscheduling data, one or more indications related to a subframe format tobe utilized by the UE 102 in uplink transmissions during particularsubframes, or any other control signaling related to the UE 102 or anyother UEs in a cell in which the communication is taking place.

The present disclosure relates at least to uplink control signalingtransmitted by a UE 102 on a PUCCH. In some examples, PUCCHtime-frequency resources are located at the edges of the total availablecell bandwidth, where each such resource consists of twelve subcarriers(e.g., one resource block) within each of the two segments (e.g. twoslots) of an uplink subframe. In order to provide frequency diversity,these frequency resources undergo frequency hopping on the slotboundary, i.e. one “resource” consists of 12 subcarriers at the upperpart of the spectrum within the first slot of a subframe and an equallysized resource at the lower part of the spectrum during the second slotof the subframe (or vice versa). If more resources are needed for theuplink Layer1/Layer2 (L1/L2) control signaling, e.g. in case of verylarge overall transmission bandwidth supporting a large number of users,additional resources blocks can be assigned next to the previouslyassigned resource blocks.

As mentioned above, uplink L1/L2 control signaling includes hybrid-ARQacknowledgements, channel-status reports, and scheduling requests.Different combinations of these types of messages are possible by usingone of available multi-segment subframe formats 22, which are capable ofcarrying different numbers of bits.

The bandwidth of one resource block during one subframe is too large forthe control signaling needs of a single terminal. Therefore, toefficiently exploit the resources set aside for control signaling,multiple terminals can share the same resource block. This is done byassigning the different terminals different orthogonal phase rotationsof a cell-specific length-12 frequency-domain sequence. The resourceused by a PUCCH is therefore not only specified in the time-frequencydomain by the resource-block pair, but also by the phase rotationapplied. Similarly to the case of reference signals, there are up totwelve different phase rotations specified, providing up to twelvedifferent orthogonal sequences from each cell-specific sequence.However, in the case of frequency-selective channels, not all the twelvephase rotations can be used if orthogonality is to be retained.Typically, up to six rotations are considered usable in a cell.

Layer 1/Layer 2 is used for hybrid-ARQ acknowledgements and schedulingrequests on the PUCCH. It is capable of carrying up to two informationbits in addition to Discontinuous Transmission (DTX), whereby if noinformation transmission was detected in the downlink, noacknowledgement is generated in the uplink. Hence, there are three orfive different combinations, depending on whether MIMO was used on thedownlink or not:

No MIMO Combination MIMO 1^(st) transport block 2^(nd) transport block 1ACK ACK ACK 2 NAK ACK NAK 3 DTX NAK ACK 4 NAK NAK 5 DTX

Currently, several PUCCH “formats” are utilized for PUCCH communicationin a particular LTE Release 13 subframe. For purposes of the presentdisclosure, these presently-utilized PUCCH formats are referred toherein as “legacy” PUCCH formats, Release 13 PUCCH formats,multi-segment (or multi-slot) subframe formats 22, or simply PUCCHformats. These legacy formats will be described below, along with thepresently proposed single-segment (e.g., single-slot) subframe formats21.

For instance, legacy PUCCH format 1 (three formats, 1, 1 a, and 1 b,exist in the current specifications, although herein they are allreferred to as format 1 for simplicity) uses the same structure in thetwo segments (e.g., slots, symbols, etc.) of a subframe. Fortransmission of a hybrid-ARQ acknowledgement, the single hybrid-ARQacknowledgement bit is used to generate a BPSK symbol (in case ofdownlink spatial multiplexing the two acknowledgement bits are used togenerate a Quadrature Phase Shift Keying (QPSK) symbol). For ascheduling request, on the other hand, the Binary Phase Shift Keying(BPSK)/QPSK symbol is replaced by a constellation point treated asnegative acknowledgement at the eNodeB. The modulation symbol is thenused to generate the signal to be transmitted in each of the two PUCCHslots.

Channel-status reports are used to provide the eNodeB with an estimateof the channel properties at the terminal in order to aidchannel-dependent scheduling. A channel-status report consists ofmultiple bits per subframe. PUCCH format 1, which is capable of at mosttwo bits of information per subframe, can obviously not be used for thispurpose. Transmission of channel-status reports on the PUCCH is insteadhandled by PUCCH format 2, which is capable of multiple information bitsper subframe (there are actually three variants in the LTEspecifications, formats 2, 2 a and 2 b, where the last two formats areused for simultaneous transmission of hybrid-ARQ acknowledgements asdiscussed below—for simplicity, they are all referred to as format 2herein). PUCCH format 2 is based on a phase rotation of the samecell-specific sequence as format 1.

PUCCH format 3 is designed for carrier aggregation purpose. The multipleACK/NACK bits are encoded to form 48 coded bits. The coded bits are thenscrambled with cell-specific (and possibly Discrete Fourier TransformSpreading Orthogonal Frequency Division Multiplexing (DFTS-OFDM) symboldependent) sequences. In PUCCH format 3, 24 bits are transmitted withinthe first slot and the other 24 bits are transmitted within the secondslot. The 24 bits per slot are converted into 12 QPSK symbols, DiscreteFourier Transform (DFT) precoded, spread across five DFTS-OFDM symbolsand transmitted within one resource block (bandwidth) and five DFTS-OFDMsymbols (time). In addition, PUCCH format 3 UE-specific spreadingsequence that enables multiplexing of up to five users within the sameresource blocks.

PUCCH formats 4 and 5 are extension of format 3 that allow more HARQdata to be transmitted. This stems from the extension of carrieraggregation in Release 13, allowing up to 32 component carriers. Format4 uses 144 blocks of QPSK symbols spread over the two slots. No cyclicshift is used so that every symbol can transmit 2 HARQ coded bits. Eachblock corresponds to one resource block (12 subcarriers) in thefrequency domain. In the time domain, the first slot is occupied by 6data OFDM symbols and 1 reference signal OFDM symbol, and the secondslot contains 5 data symbol and 2 reference symbols.

PUCCH format 5 is similar to format 4 and uses 72 QPSK symbols spreadover two slots. Size 2 code division multiplexing allows themultiplexing of users. Format 5 occupies one resource block (12subcarrier) in the frequency domain. In the time domain, the two slotsare each occupied by 6 data OFDM symbols and 1 reference signal OFDMsymbol.

In addition, the use of LTE carrier aggregation (CA), introduced inRelease 10 and enhanced in Release 11, offers means to increase the peakdata rates, system capacity and user experience by aggregating radioresources from multiple carriers that may reside in the same band ordifferent bands and, for the case of inter-band TDD CA, may beconfigured with different UL/DL configurations. In Release 12, carrieraggregation between TDD and FDD serving cells is introduced to supportUE connecting to them simultaneously.

In Release 13, LAA (Licensed-Assisted Access) has attracted significantinterest for its potential to extend the LTE carrier aggregation featuretoward capturing the spectrum opportunities of unlicensed spectrum inthe 5 GHz band. WLAN operating in the 5 GHz band already supports 80 MHzin the field and 160 MHz is to follow in Wave 2 deployment of IEEE802.11ac. There are also other frequency bands, such as 3.5 GHz, whereaggregation of more than one carrier on the same band is possible, inaddition to the bands already widely in use for LTE. Enabling theutilization of at least similar bandwidths for LTE in combination withLAA as IEEE 802.11ac Wave 2 will support calls for extending the carrieraggregation framework to support more than 5 carriers. The extension ofthe CA framework beyond 5 carriers was approved to be one work item forLTE Release 13. The objective is to support up to 32 carriers in both ULand DL.

Compared to single-carrier operation, a UE operating with CA has toreport feedback for more than one DL component carrier. Meanwhile, a UEdoes not need to support DL and UL CA simultaneously. For instance, thefirst release of CA-capable UEs in the market only supports DL CA (andnot UL CA). This is also the underlying assumption in the 3GPP RAN4standardization. Therefore, an enhanced UL control channel, i.e. PUCCHformat 3 was introduced for CA during Release 10 timeframe. However, inorder to support more component carriers in Release 13, the UL controlchannel capacity becomes a limitation;

In carrier aggregation, PUCCH transmission can be done with twodifferent ways. The first method is based on the use of PUCCH format 3that is based on DFTS-OFDM.

The second CA PUCCH method is called channel selection. The basicprinciple is that the UE is assigned a set of PUCCH format 1 a/1 bresources. The UE then selects one of resources according to theACK/NACK sequence the UE should transmit. On one of the assignedresource the UE would then transmit a QPSK or BPSK. The eNB detectswhich resource the UE uses and which QPSK or BPSK value the UE fed backon the used resource, and combines this into a HARQ response forassociated DL cells.

As discussed briefly above, delays associated with SRS transmission(e.g., in SRS frequency hopping scenarios, have been known to cause adelay that meets a certain criterion (e.g., has a duration greater than(or sometimes also equal to) a threshold duration) that if met, causesthe network node 106 and/or the UE 102 to determine that one or moreslots should be dropped (i.e., the uplink control data transmissionsover the PUCCH for these one or more slots are canceled or delayed).Although helping to ensure that collision is avoided, these delaysintroduce performance losses and, potentially, the loss of datatransmissions altogether (e.g., the transmissions for the dropped slotsare not subsequently transmitted).

The discussion on SRS based carrier switching/hopping started in RAN1#84b [1-3]. In the present invention, the impact of handling collisions(between transmitting SRS on another CC and PUCCH or PUSCH channels inthe CA CC from which the switching is done) is discussed and severalnovel solutions to handle the dropping of slots are proposed.

The impact of collision is highly dependent on how long interruptiontime is introduced by the switching of SRS. A few microseconds can behandled on the requirement level as a RAN4 issue. Requirementspecifications (e.g., 3GPP 36.101) have specified transition delaytolerances to allow power amplifiers to switch between PUCCH and SRSpower levels. If the switching time is within the same order ofmagnitude, RAN4 can adjust the requirements.

If the switching delay meets a criterion (e.g., is on the order of aSC-OFDM symbol length or more, etc.) there can be an impact in networkperformance and capacity at least in term of PUCCH/PUSCH throughputwhich in turn leads to drops in network user capacity. SRS-based carrierswitching does not currently have a standardized solution to handledropping of slots which cannot be transmitted due to the interruptiontime needed to switch between component carriers.

Accordingly, one non-limiting objective of the example embodimentsdescribed herein is to maintain as much of a payload of a control signalsubframe when one of the two segments (e.g., slots, symbols, etc.) mustbe dropped (i.e., transmissions scheduled for the dropped segment/slotare not transmitted). To meet this end, the present applicationdescribes several non-limiting subframe structures that utilize onesegment instead of the two segments (e.g., where the segment can be aslot of a Release 13 subframe, for instance, though this is not alimiting aspect). Such a structure is illustrated in subframe N of FIG.1 , wherein uplink control transmissions occur in one of the slots (inFIG. 1 , slot 0 of subframe N, although they may occur alternatively inslot 1) and do not occur in the other slot (in FIG. 1 , slot 0 ofsubframe N). For instance, in some embodiments herein, PUCCH formats 1,1 a, 1 b, 3, 4, and 5 (described above) are compressed to one of the twoslots that Release 13 PUCCH formats occupy (see, e.g., slots 0 and 1 ofsubframe N−1 of FIG. 1 , which has a multi-segment (specifically,multi-slot) subframe format according to, for example, those utilizedpresently in Release 13 implementations). In some embodiments, PUCCHChannel State Information (CSI) reporting payloads are halved tocompensate for the loss of half the PUCCH resource and power offsets cancompensate for the loss of the second slot. Release 13 reference signaldesigns, channel coding, interleaving, rate matching, and slotstructures can be used along with the above aspects. As such, thepresent embodiments allows UEs/network nodes to communicate controlinformation during a single segment (e.g., single slot) in a subframewhen the UE must drop one slot (as it is the case in SRS carrier basedswitching).

Accordingly, the description below describes several potentialsingle-segment subframe formats 21, which can be selected for use in oneor more subframes by network node 106 or UE 106, for instance, byprocessing executed in a control signal manager 32 of the UE 102 or ascheduler 28 of the network node. For purposes of the presentdisclosure, the term “segment” (as used in the terms single-segment,multi-segment, and the like) may refer to any time and/or frequencyresource group used to model a wireless communication channel, such as,but not limited to, a slot, a symbol, or any other related entity knownin the art.

In some examples described herein, the network node 106 and UE 102 maynegotiate as to which of a single-segment subframe format 21 ormulti-segment subframe format 22 to utilize, or one of the network node106 or the UE 102 may be charged with making such a determination. Insome examples, this determination may include determining whether an SRSis to be transmitted by the UE during a particular segment and/orsubframe, whether frequency hopping between segments/subframes isutilized by the UE 102, and/or whether a delay associated with the SRStransmission or frequency hopping causes or may cause a delay that meetsa particular criterion for selecting a single-segment subframe format 21instead of a multi-segment subframe format 22.

In a further aspect, the control signal manager 32 and/or the scheduler28 may be configured to adjust a power level associated withtransmissions during a slot when a single-segment subframe format 21 isselected for a subframe. As described in further detail below, this mayinclude increasing the power of transmissions during the single segmentof the subframe by a residual amount corresponding to power that will beunused for transmissions in the other slot of the subframe.

In addition, as introduced above, when a single-segment subframe format21 is selected instead of a multi-segment subframe format 22, thenetwork node 106 and/or UE 102 may choose between multiple potentialsingle-segment subframe formats 21 available to be utilized. Examples ofthese available single-segment subframe formats will now be described indetail, some of which are described in relation to the multi-segmentsubframe formats 22 described above (i.e., Release 13 two-slot subframeformats). In certain example embodiments, the number ofacknowledgement/negative acknowledgement (A/N or ACK/NACK) bits carriedin single-segment PUCCH formats 1, 1 a, and 1 b is the same as thecorresponding Release 13 (i.e. “legacy”) formats, as the second slot cancarry the same information as slot 1. This can be true when channelselection is or is not configured for the UE. In addition, power can beadjusted to account to the available power of the dropped slot, i.e. thefirst slot is now scaled with additional power previously available forthe second slot.

In addition, according to the present disclosure, formats 2, 2 a, and 2b can carry from 20 to 22 bits of payload (20 coded bits of CSI plus upto two bits of HARQ-ACK), corresponding to 10 CSI bits and 2 bits ofHARQ-ACK. In order to carry that payload over a single segment, such asa single slot, it is proposed to use the coding and slot structure fromPUCCH format 3 in the slot.

The slot structure and coding of PUCCH format 3 could replace formats 2,2 a, and 2 b, and therefore be labeled PUCCH format 2 c′. The same 11bit Reed-Muller code would be used for CSI, and with CSI+up to 2 bitA/N. If used for TDD, format 2 c may be used in subframes where only A/Nfor the primary cell is needed, and when the UE is configured withHARQ-ACK bundling, HARQ-ACK multiplexing or PUCCH format 1 b withchannel selection, since the number of A/N bits can be 2 in such cases.Power is adjusted to account to the available power of the dropped sloti.e. the first slot is now scaled with additional power previouslyavailable for the second slot.

Single-Segment PUCCH Format 3 (New Format 3 b or 2 d)

In example embodiments of the present disclosure, if multiplexing morethan 2 A/N bits with CSI is desired in Release 13 LTE systems, legacyPUCCH format 3 may be used. If, however, a slot must be dropped, asingle-segment format 3 can be used. For this single-segment subframeformat, PUCCH dropping rules for format 3 (e.g., as defined in section7.3.2 of 3GPP 36.213) are used, except that the rules that drop PUCCHcontent at 22 bits now drop with 12 bits. Furthermore, instead of 20bits HARQ-ACK with 1 bit SR as in legacy PUCCH format 3, at most 10 bitsHARQ-ACK and 1 bit SR is carried on single-segment PUCCH 3 of thepresent disclosure. In some embodiments, the 11 bit Reed-Muller codecould still be used, with corresponding new rules for coding less than11 bits containing both A/N and CSI, since A/N is not multiplexed withCSI for less than 11 bits in Release 13. In addition, power can beadjusted to account to the available power of the dropped slot i.e. thefirst slot is now scaled with additional power previously available forthe second slot.

In any event, the maximum of transmitted HARQ-ACK bits in thesingle-segment PUCCH format 3 is less than in the legacy PUCCH format 3,and so may be considered as a smaller version of PUCCH format 3, e.g.‘format 3 b’. Alternatively, given that the payload size is similar toPUCCH format 2, it may be considered as a new PUCCH format 2 that allowsCSI and HARQ-ACK to be multiplexed, e.g. a ‘format 2 d’.

Single-Segment PUCCH Formats 4 and 5

PUCCH format 5 (with normal CP) can carry 12 subcarriers/2 CDM users×6symbols/slot×2 slots×2 bit QPSK=144 channel bits. If only one slot isused, then 72 channel bits can be carried.

So, the number of channel bits when PUCCH format 5 is shortened to oneslot can somewhat exceed the 48 bits in PUCCH format 3. A simplesolution (similar to ‘format 2 c’ above) then would be to create a newPUCCH format using a single-segment of PUCCH format 5 that exactlyfollows the behavior of PUCCH format 3 with respect to coding and CSIdropping rules. Such a new format would carry no more than 21 bitspayload. This new format could be used to construct a second version ofPUCCH format 3, e.g. a PUCCH format 3 a′, and be used in place of PUCCHformat 3 for when a UE needs to transmit PUCCH format 3 but must alsotransmit only in one slot in a given subframe. For example, when a UEconfigured for PUCCH formats 3, 4, or 5 determines that PUCCH format 3should be used (according to Release 13), but only one slot is availableto transmit PUCCH, then PUCCH format 3 a would be used instead.

Similar to PUCCH format 5, format 4 allows several blocks of 144 bits(72QPSK symbols) per slots, or 288 coded bits per subframes.

Single-segment subframe formats based on PUCCH formats 4 and 5, e.g.‘format 4 a’, and ‘format 5 a’ could behave similarly, transmitting inonly one slot while using Release 13 dropping rules changed tocompensate for half of the REs being available as payload. For example,the dropping criterion with HARQ-ACK and CSI present for PUCCH format 4configured with two sizes, changes to:(O ^(ACK) +O ^(SR) +O _(P-CSI) +O _(CRC))≤min(M _(RB,1) ^(PUCCH4) ,M_(RB,2) ^(PUCCH4))·N _(SC) ^(RB) ·N _(symb) ^(PUCCH4) ·N _(slot)^(PUCCH) ·rWhere a new parameter N_(slot) ^(PUCCH)∈{1, 2} is introduced.

For PUCCH format 4 or 5, this parameter is set to N_(slot) ^(PUCCH)=1 insubframes where UE can only transmit in one segment (e.g., one slot) ofthe serving cell, and N_(slot) ^(PUCCH)=2 otherwise. In some embodimentsof the present disclosure, transmitting using legacy (i.e., Release 13)PUCCH format 4 or format 5 in only one slot is still considered PUCCHformat 4 or format 5. In such cases, the UE can be configured with PUCCHformat 4 or PUCCH format 5, and informed by the network that it shouldtransmit PUCCH format 4 or format 5 using one segment in certainsubframes, such as those where the UE may switch to another carrier totransmit SRS. The network may inform the UE of this by indicating to theUE that N_(slot) ^(PUCCH)=2 should be used in certain subframes, such asthe switching subframes. In addition, power can be adjusted to accountto the available power of the dropped slot, for example such that thefirst segment is scaled with additional power previously available forthe second segment in legacy subframe formats.

Furthermore, because legacy PUCCH format 5 supports a variety of coderates (from 0.08 to 0.8), single-segment PUCCH format 5 as describedherein can allow from 4 to 48 bits payload (e.g., information bits).Therefore, if a UE transmits using the legacy PUCCH format 3 (20 bitsHARQ plus a one-bit scheduling request) but is constrained to use onlyone segment, the single-segment format 5 could be utilized as a viableimprovement over existing formats.

As introduced above, one or both of the network node 106 and the UE 102may adjust the transmission power for control signal transmissions inthe single utilized slot of a single-segment subframe format.Embodiments that adjust power to account for the available power of thedropped slot may use an additional factor in the UE power controlcalculations. One such embodiment uses a factor Δ_(slot)(i) thatincreases the transmitted power of PUCCH in subframes where the UEtransmits a single-segment PUCCH format relative to subframes where theUE transmits a Release 13 PUCCH format. This may be expressed as

$\begin{matrix}{{P_{PUCCH}^{\prime}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{P_{PUCCH}(i)} + {\Delta_{slot}(i)}}\end{Bmatrix}}} & \end{matrix}$where:

-   -   min{a, b} is the minimum of a and b, where a and b are real        numbers,    -   P′_(PUCCH)(i) is the power the UE should transmit in dB after        being adjusted for operating with a single PUCH slot format        configured, and    -   P_(PUCCH)(i) is calculated according to section 5.1.2.1 of 3GPP        TS 36.213 rev. 13.2.0

Furthermore, Δ_(slot)(i) is 0 in subframes where UE transmits Release 13PUCCH formats, and is a non-zero value in a subframe when the UEtransmits a single-segment PUCCH format. The non-zero value may be 3 dBin some embodiments. In other embodiments the value of Δ_(slot)(i) insubframes where the UE transmits a single-segment PUCCH format is set byhigher layers, for example using an RRC configured parameter or a valueprovided in a MAC control element.

In addition, the equation above for P′_(PUCCH)(i) may be equivalentlyexpressed by incorporating Δ_(slot)(i) in the Release 13 power controlexpressions for P_(PUCCH) (i). For example, If serving cell c is theprimary cell, for PUCCH format 1/1 a/1 b/2/2 a/2 b/3, the setting of theUE Transmit power P_(PUCCH) for the physical uplink control channel(PUCCH) transmission in subframe i for serving cell c is defined inRelease 13 as:

${P_{PUCCH}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\\begin{matrix}{P_{0{\_ PUCCH}} + {PL}_{c} + {h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} +} \\{{\Delta_{F\_ PUCCH}(F)} + {\Delta_{TxD}\left( F^{\prime} \right)} + {g(i)}}\end{matrix}\end{Bmatrix}}$

This can be extended to support when single-segment PUCCH formats can betransmitted by the UE by including Δ_(slot)(i) as shown below:

${P_{PUCCH}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\\begin{matrix}{P_{0{\_ PUCCH}} + {PL}_{c} + {h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} +} \\{{\Delta_{F\_ PUCCH}(F)} + {\Delta_{TxD}\left( F^{\prime} \right)} + {g(i)}}\end{matrix}\end{Bmatrix}}$

In addition to adjusting power levels for single-segment subframecontrol signal transmissions, the network node 106 (or in some cases,the UE 102 based on a predetermined pattern/timing reference) can selecta particular slot (e.g., slot 0 or slot 1 of the subframes of FIG. 1 )during which control signal transmission occurs and, accordingly, theslot during which no such control signal transmission occurs. Forexample, because existing PUCCH formats (including formats 1, 1 a, 1 b,2, 2 a, 2 b, 3, 4, and 5) frequency hop once per slot, it is notpossible to support PUCCH frequency hopping in one subframe. However,the Release 13 PUCCH resource principles can be used, where a PUCCH'stransmission in even slots is at the low end of the band, and at thehigh end of the band in odd slots, i.e. according to the following:

$n_{PRB} = \left\{ \begin{matrix}\left\lfloor \frac{m}{2} \right\rfloor & {{{if}\left( {m + {n_{s}\ {mod}2}} \right)\ {mod}2} = 0} \\{N_{RB}^{UL} - 1 - \left\lfloor \frac{m}{2} \right\rfloor} & {{{if}\left( {m + {n_{s}\ {mod}2}} \right){mod}2} = 1}\end{matrix} \right.$

In such cases, a UE transmitting single-segment PUCCH formats 1, 1 a, 1b, 4 or 5, or the new formats 2 c, 3 a, 4 a, or 5 a, can be allocatedeither the even or odd slot to transmit PUCCH in a given subframe, andaccordingly could transmit only when n, mod 2=0 or when n, mod 2=1,respectively. Single-segment PUCCH resource could therefore be definedas the Release 13 PUCCH format 1, 1 a, 1 b, 3, 4, or 5 resource pluswhether the UE transmits a single-segment PUCCH format in a givensubframe when n, mod 2=0 or when n, mod 2=1. Then existing PUCCHresource allocation mechanisms (implicit allocation, ARI, and ARO) canbe used to determine the PRBs for both slots, and the RRC configuredslot selects which RB(s) the UE will transmit on.

Therefore, as described above, aspects of the presently disclosedembodiments and techniques include selecting and utilizingsingle-segment subframe formats, each of which may constitute ashortened format relative to existing, or “legacy” formats. This allowsthe network node 106 and UE 102 to maximize the signaling payload thatcan be communicated in a given timeframe, while advantageously utilizingcoding methods with which the devices are already configured tocommunicate. In addition, the aspects of the present disclosureintroduce techniques for optimizing transmission power for transmissionsduring a single subframe slot and for selecting a slot so as to maximizethe effective slot usage on a cell-wide basis (i.e., for multiple usersin a particular cell).

FIG. 2 illustrates an example method 200 performed by one or more UEs102 for control signal transmission. The method 200 may include, atblock 202, selecting a single-segment subframe format as an uplinktransmission format for a subframe instead of a multi-segment subframeformat. In addition, at block 204, the UE may transmit one or morecontrol signals on an uplink control channel using the single-segmentsubframe format.

In addition, although not explicitly recited in FIG. 2 , method 200 mayinclude one or more additional aspects, such as the UE selecting thesubframe format by recognizing that a component carrier (CC) switch isto be performed for a sounding reference signal (SRS) in a multi-segmentsubframe, determining that the CC switch would introduce a transmissiondelay that meets a time duration criterion, and selecting the uplinktransmission format in response to determining that the time durationcriterion is met. In an aspect, the single-segment subframe formatcomprises a bit-reduced version of at least one type of multi-segmentsubframe format. Furthermore, the single-segment subframe formatutilizes a coding method utilized by at least one type of multi-segmentsubframe format. The selecting may include selecting the single-segmentsubframe format from a set of single-segment subframe formats. Themethod 200 may further include setting a power level at which totransmit the one or more control signals by utilizing transmission powerotherwise allocated to a slot of the subframe that is not used fortransmission of the one or more control signals according to thesingle-segment subframe format and transmitting the one or more controlsignals at the power level. The power level may be a power level greaterthan another power level utilized for an associated transmission of theone or more control signals when the multi-segment subframe is utilized.Moreover, transmitting the one or more control signals using thesingle-segment subframe format may include selecting a single segment oftwo possible segments (e.g., slots, symbols, etc.) of the subframeduring which the one or more control signals are to be transmitted.Method 200 may further include receiving, from a network node, anindication of which of a plurality of segments the uplink controlchannel should be transmitted using the single-segment subframe format,receiving, from the network node, an indication of a control channelfrequency resource to be used to transmit the one or more controlsignals, the indication comprising one or more of a location of adownlink control channel received by the UE, and a resource indicationcarried within downlink control information on the downlink controlchannel. Furthermore, the method may include determining a physicalresource block in which the one or more should be transmitted using thesingle-segment subframe format using the indication of the controlchannel resource and the slot in which the control channel is to betransmitted.

FIG. 3 illustrates an example method 300 performed by one or morenetwork nodes 106 for controlling transmission of one or more controlsignals by a UE 102. For example, the method 300 includes the networknode 106 selecting a single-segment subframe format as an uplinktransmission format for the one or more control signals transmitted bythe UE in a subframe instead of a multi-segment subframe format at block302. In addition, at block 304, the network node 106 transmits anindication to the UE indicating that the one or more control signals areto be transmitted on an uplink control channel using the single-segmentsubframe format. Furthermore, at block 306, the network node 106receives the one or more control signals on the uplink control channelaccording to the single-segment subframe format, for example, based onthe network node 106 transmitting the indication to the UE at block 304.

FIG. 4A illustrates a UE 102, implemented in accordance with one or moreembodiments. As shown, the UE 102 includes processing circuitry 400(which may include at least one processor) and communication circuitry410. The communication circuitry 410 is configured to transmit and/orreceive information to and/or from one or more network nodes 106 via anycommunication technology. Such communication may occur via one or moreantennas that are either internal or external to the UE 102. Theprocessing circuitry 400 is configured to perform processing describedabove, e.g., in FIG. 2 , such as by executing instructions stored inmemory 420. The processing circuitry 400 in this regard may implementcertain functional means, units, or modules.

FIG. 4B illustrates a UE 102 implemented in accordance with one or moreother embodiments. As shown, the UE 102 implements various functionalmeans, units, or modules, e.g., via the processing circuitry 400 in FIG.4A and/or via software code. These functional means, units, or modules,e.g., for implementing the method in FIG. 2 , include for instance aselecting unit or module 430 for selecting a single-segment subframeformat as an uplink transmission format for a subframe. Also included isa transmitting unit or module 440 for transmitting one or more controlsignals on an uplink control channel using the single-segment subframeformat.

FIG. 5A illustrates a network node 106, such as a base station, eNB, orother network-side devices, implemented in accordance with one or moreembodiments. As shown, the network node 106 includes processingcircuitry 500 and communication circuitry 510. The communicationcircuitry 510 is configured to transmit and/or receive information toand/or from one or more UEs 102 and/or one or more other nodes, e.g.,via any communication technology. Such communication may occur via oneor more antennas that are either internal or external to the networknode 106. The processing circuitry 500 is configured to performprocessing described above, e.g., in FIG. 3 , such as by executinginstructions stored in memory 520. The processing circuitry 500 in thisregard may implement certain functional means, units, or modules.

FIG. 5B illustrates a network node 106 implemented in accordance withone or more other embodiments. As shown, the network node 106 implementsvarious functional means, units, or modules, e.g., via the processingcircuitry 500 in FIG. 5A and/or via software code. These functionalmeans, units, or modules, e.g., for implementing the method in FIG. 3 ,include for instance a selecting unit or module 530 for selecting asingle-segment subframe format as an uplink transmission format for a UEfor a subframe. Also included is a transmitting unit or module 540 fortransmitting an indication to the UE 102 indicating that one or morecontrol signals on an uplink control channel are to be transmitted usingthe single-segment subframe format. In addition, a receiving unit ormodule 550 is included for receiving the one or more control signals onthe uplink control channel.

Those skilled in the art will also appreciate that embodiments hereinfurther include corresponding computer programs. A computer programcomprises instructions which, when executed on at least one processor orprocessing circuitry of a node, cause the node to carry out any of therespective processing described above. A computer program in this regardmay comprise one or more code modules corresponding to the means orunits described above. Embodiments further include a carrier containingsuch a computer program. This carrier may comprise one of an electronicsignal, optical signal, radio signal, or computer readable storagemedium. In this regard, embodiments herein also include a computerprogram product stored on a non-transitory computer readable (storage orrecording) medium and comprising instructions that, when executed by aprocessor, or processing circuitry, of a network node or UE, cause thenode or UE to perform as described above. Embodiments further include acomputer program product comprising program code portions for performingthe steps of any of the embodiments herein when the computer programproduct is executed by a computing device. This computer program productmay be stored on a computer readable recording medium.

Furthermore, the processing or functionality of network node 106 may beconsidered as being performed by a single instance or device or may bedivided across a plurality of instances of network node 106 that may bepresent in a given network/environment such that together the deviceinstances perform all disclosed functionality. In addition, network node106 may be any known type of device associated with a wirelesscommunication network, radio communication network, or content deliverynetwork, generally, that is known to perform a given disclosed processesor functions thereof. Examples of such network nodes include eNBs, gNBs(or other types of base stations or access points), Mobility ManagementEntities (MMEs), gateways, servers, and the like.

In any scenario discussed above, the UE 102 herein may be, or may becomprised of any wireless communication device that is able tocommunicate wirelessly with a wireless communication network, and mayinclude, in some examples, mobile devices such as mobile phones, PDAs,tablets, computers (mobile or otherwise) laptops, or the like. Inaddition the UE 102 may comprise an Internet-of-Things device, e.g. adevice that performs monitoring or measurements, and transmits theresults of such monitoring measurements to another device or a network.Particular examples of such machines are power meters, industrialmachinery, or home or personal appliances, e.g. refrigerators,televisions, personal wearables such as watches etc. In other scenarios,a wireless communication device as described herein may be comprised ina vehicle and may perform monitoring and/or reporting of the vehicle'soperational status or other functions associated with the vehicle.

The 3GPP has issued agreements concerning 5G New Radio (NR) terminologyin the period between the earliest priority date and the filing date ofthe present disclosure. NR terminology and LTE terminology coincide to aconsiderable extent. For instance, a resource element (RE) remains 1subcarrier×1 OFDM symbol. Yet some terms known in LTE have been given anew meaning in NR. The present disclosure, including the claims, appliesprefixes “LTE” and “NR” to clarify the relevant technical context. Forinstance, an LTE subframe lasting 1 ms contains 14 OFDM symbols fornormal CP, whereas an NR subframe has a fixed duration of 1 ms and maytherefore contain a different number of OFDM symbols for differentsubcarrier spacings. An LTE slot corresponds to 7 OFDM symbols fornormal CP, whereas an NR slot may correspond to 7 or 14 OFDM symbols; at15 kHz subcarrier spacing, a slot with 7 OFDM symbols occupies 0.5 ms.Concerning NR terminology, reference is made to 3GPP Technical Report38.802 v14.0.0 and to Technical Specifications to appear in the 38series.

A non-prefixed term in this disclosure is to be understood in the LTEsense unless otherwise stated. However, any term designating an objector operation known from LTE is expected to be reinterpreted functionallyin view of NR specifications. For instance, an LTE radio frame may befunctionally equivalent to an NR frame, considering that both have aduration of 10 ms. An LTE subframe may be functionally equivalent to anNR slot with a corresponding number of OFDM symbols. An LTE eNB may befunctionally equivalent to an NR gNB, since their functionalities asdownlink transmitter are at least partially overlapping. A resourceblock (RB), which comprises 12 subcarriers×1 slot, is the schedulingunit in LTE, that is, the smallest assignable resource. The LTE RB iscomparable to the smallest assignable resource in NR, which is theshortest mini-slot, with a single OFDM symbol. Therefore, even thoughsome embodiments of this disclosure have been described usingLTE-originated terminology, they remain fully applicable to NRtechnology.

The example embodiments described in the present disclosure may, ofcourse, be carried out in other ways than those specifically set forthherein without departing from essential characteristics of theinvention. The present embodiments are to be considered in all respectsas illustrative and not restrictive, and all changes coming within themeaning and equivalency range of the appended claims are intended to beembraced therein.

The invention claimed is:
 1. A method performed by a user equipment forcontrol signal transmission, comprising: selecting a single-segmentsubframe format as an uplink transmission format for a subframe insteadof a multi-segment subframe format, wherein the single-segment subframeformat consists of a single transmission segment and the multi-segmentsubframe format consists of multiple instances of the transmissionsegment; selecting a segment from among two or more segments in thesubframe for transmission of control signals; and transmitting one ormore control signals on an uplink control channel in the selectedsegment using the single-segment subframe format.
 2. The method of claim1, wherein the transmission segment is a slot.
 3. The method of claim 1,wherein the transmission segment is a symbol.
 4. The method of any ofclaim 1, wherein the selecting further comprises: recognizing that acomponent carrier (CC) switch is to be performed for a soundingreference signal (SRS) in a multi-segment subframe; determining that theCC switch would introduce a transmission delay that meets a timeduration criterion; and selecting the uplink transmission format inresponse to determining that the time duration criterion is met.
 5. Themethod of any of claim 1, wherein the single-segment subframe formatcomprises a bit-reduced version of at least one type of multi-segmentsubframe format.
 6. The method of any of claim 1, wherein thesingle-segment subframe format utilizes a coding method utilized by atleast one type of multi-segment subframe format.
 7. The method of any ofclaim 1, wherein selecting the single-segment subframe format comprisesselecting the single-segment subframe format from a set ofsingle-segment subframe formats.
 8. The method of any of claim 1,wherein the single-segment subframe format has an associated codingscheme utilized by at least one multi-segment subframe format.
 9. Themethod of any of claim 1, wherein transmitting the one or more signalscomprises: setting a power level at which to transmit the one or morecontrol signals by utilizing transmission power otherwise allocated to asegment of the subframe that is not used for transmission of the one ormore control signals according to the single-segment subframe format;and transmitting the one or more control signals at the power level. 10.The method of any of claim 1, wherein the power level comprises a powerlevel greater than another power level utilized for an associatedtransmission of the one or more control signals when the multi-segmentsubframe format is utilized.
 11. The method of any of claim 1, whereintransmitting the one or more control signals using the single-segmentsubframe format comprises selecting a single slot of two possible slotsof the subframe during which the one or more control signals are to betransmitted.
 12. The method of any of claim 1, further comprisingreceiving, from a network node, an indication of which of a plurality ofslots the uplink control channel should be transmitted using thesingle-segment subframe format; receiving, from the network node, anindication of a control channel frequency resource to be used totransmit the one or more control signals, the indication comprising oneor more of: a location of a downlink control channel received by the UE,and a resource indication carried within downlink control information onthe downlink control channel; and determining a physical resource blockin which the one or more should be transmitted using the single-segmentsubframe format using the indication of the control channel resource andthe segment in which the control channel is to be transmitted.
 13. Themethod of any of claim 1, wherein the multi-segment subframe formatcomprises pilot time slots.
 14. The method of claim 12, wherein themulti-segment subframe format comprises an uplink pilot time slot and adownlink time slot and optionally a guard period.
 15. The method ofclaim 13, wherein the single-segment subframe format comprises atransmission of the one or more control signals on the and at least oneretuning period, in which UE transmission is not required.
 16. Themethod of any of claim 13, wherein at least a part of a one-slotremainder of the not-selected multi-segment subframe format is used fortransmitting a downlink pilot signal or uplink pilot signal.
 17. Themethod of claim 15, wherein said remainder further comprises a retuningperiod, in which UE transmission is not required.
 18. The method of anyof claim 13, wherein the one or more control signal is a SRS.
 19. Themethod of claim 18, wherein the SRS is transmitted in non-final and/ornon-initial symbols of the single-segment subframe format.
 20. Themethod of any of claim 13, further comprising recognizing that a CCswitch is to be performed from a CC configured for Time DivisionDuplexing (TDD).
 21. The method of any of claim 13, further comprisingrecognizing that the UE belongs to an interruption time class, which isselected from a plurality of predefined classes, wherein theinterruption time class to which the UE belongs specifies a maximuminterruption time of less than 350 μs or specifies a maximuminterruption time of less than 5 symbols.
 22. A user equipment (UE)configured to: select a single-segment subframe format as an uplinktransmission format for a subframe instead of a multi-segment subframeformat, wherein the single-segment subframe format consists of a singletransmission segment and the multi-segment subframe format consists ofmultiple instances of the transmission segment; select a segment fromamong two or more segments in the subframe for transmission of controlsignals; and transmit one or more control signals on an uplink controlchannel in the selected segment using the single-segment subframeformat.
 23. A user equipment (UE) comprising: processing circuitry and amemory, the memory containing instructions executable by the processingcircuitry whereby the UE is configured to: select a single-segmentsubframe format as an uplink transmission format for a subframe insteadof a multi-segment subframe format, wherein the single-segment subframeformat consists of a single transmission segment and the multi-segmentsubframe format consists of multiple instances of the transmissionsegment; and select a segment from among two or more segments in thesubframe for transmission of control signals; and transmit one or morecontrol signals on an uplink control channel in the selected segmentusing the single-segment subframe format.
 24. A computer programcomprising non-transitory computer readable storage medium instructionswhich, when executed by at least one processor of a user equipment (UE),causes the UE to: select a single-segment subframe format as an uplinktransmission format for a subframe instead of a multi-segment subframeformat, wherein the single-segment subframe format consists of a singletransmission segment and the multi-segment subframe format consists ofmultiple instances of the transmission segment; and select a segmentfrom among two or more segments in the subframe for transmission ofcontrol signals; and transmit one or more control signals on an uplinkcontrol channel in the selected segment using the single-segmentsubframe format.
 25. A method performed by a network node forcontrolling transmission of one or more control signals by a userequipment (UE), comprising: selecting a single-segment subframe formatas an uplink transmission format for the one or more control signalstransmitted by the UE in a subframe instead of a multi-segment subframeformat, wherein the single-segment subframe format consists of a singletransmission segment and the multi-segment subframe format consists ofmultiple instances of the transmission segment; selecting a segment fromamong two or more segments in the subframe for transmission of controlsignals; and transmitting an indication to the UE indicating that theone or more control signals are to be transmitted on an uplink controlchannel in the selected segment using the single-segment subframeformat; and receiving the one or more control signals on the uplinkcontrol channel in the selected segment according to the single-segmentsubframe format.
 26. A network node configured to: select asingle-segment subframe format as an uplink transmission format for theone or more control signals transmitted by the UE in a subframe insteadof a multi-segment subframe format, wherein the single-segment subframeformat consists of a single transmission segment and the multi-segmentsubframe format consists of multiple instances of the transmissionsegment; select a segment from among two or more segments in thesubframe for transmission of control signals transmit an indication tothe UE indicating that the one or more control signals are to betransmitted on an uplink control channel in the selected segment usingthe single-segment subframe format; and receive the one or more controlsignals on the uplink control channel in the selected segment accordingto the single-segment subframe format.
 27. A network node comprising:processing circuitry and a memory, the memory containing instructionsexecutable by the processing circuitry whereby the network node isconfigured to: select a single-segment subframe format as an uplinktransmission format for the one or more control signals transmitted bythe UE in a subframe instead of a multi-segment subframe format, whereinthe single-segment subframe format consists of a single transmissionsegment and the multi-segment subframe format consists of multipleinstances of the transmission segment; select a segment from among twoor more segments in the subframe for transmission of control signals;transmit an indication to the UE indicating that the one or more controlsignals are to be transmitted on an uplink control channel in theselected segment using the single-segment subframe format; and receivethe one or more control signals on the uplink control channel in theselected segment according to the single-segment subframe format.
 28. Anetwork node comprising: A first module to select a single-segmentsubframe format as an uplink transmission format for the one or morecontrol signals transmitted by the UE in a subframe instead of amulti-segment subframe format, wherein the single-segment subframeformat consists of a single transmission segment and the multi-segmentsubframe format consists of multiple instances of the transmissionsegment; a second module to transmit an indication to the UE indicatingthat the one or more control signals are to be transmitted on an uplinkcontrol channel using the single-segment subframe format; and a thirdmodule to receive the one or more control signals on the uplink controlchannel according to the single-segment subframe format.
 29. A computerprogram comprising non-transitory computer readable storage mediuminstructions which, when executed by at least one processor of a networknode, causes the network node to: select a single-segment subframeformat as an uplink transmission format for the one or more controlsignals transmitted by the UE in a subframe instead of a multi-segmentsubframe format, wherein the single-segment subframe format consists ofa single transmission segment and the multi-segment subframe formatconsists of multiple instances of the transmission segment; transmit anindication to the UE indicating that the one or more control signals areto be transmitted on an uplink control channel using the single-segmentsubframe format; and receive the one or more control signals on theuplink control channel according to the single-segment subframe format.